The format of a text record exported by Go Recorder, and suitable for importation by Go Recorder follows. See the example game records.

Each line of text is a command, move, notation, variation, game comment or documentation comment; lines are separated by carriage returns or tabs (not line feeds). Within a line, spaces are used to separate words.

A command starts with 3 bullet characters  
		(bullet is ascii $A5 character , option-8 on the Macintosh or Newton keyboard))

The first line of text must be 
 Go Recorder
This is used to mark a Notes entry as a Go Recorder game

The last line should be
 End game

The other commands currently available are:

 Title: <your title>
where <your title> is the game title (do not type the <> characters). This should appear as the second line of the text record if it is used at all.

 Header: <your header>
<your header> is the text to appear in Entry 0, that is, at the top of the game as displayed on the Newton. If there is no header command, the date and time the game is created on the Newton will be used. Typically this header includes players names, dates etc. This command should appear early in the record.

 Show numbers: <m> to <n>
where  m  and  n  are the first and last moves to be displayed with numbers. This command is optional, and may appear anywhere in the record.

 Set: Autocapture on/off
sets a corresponding preference for the game display. Useful for a game record which does not have captures included in the text (see below). Only the "off" variant is recorded by "Export to Note" since "on" is the default. 

 Set: Board plain/lettered
sets the board style. Only "Board lettered" is recorded since plain is the default. 

 Set: Play/Edit
sets the move information display style. "Edit" is the default, but "Play" is better for recorded games, problems and so on, as the game is then protected from changes. 

A move entry looks like this:
<optional number> B T16 <optional notation> <optional comment> <optional captures>
This would be for a Black stone at T16; similarly  W Q1  dewscribes a White stone at Q1 of course. The optional parts are:

<optional number>  20: denotes move number 20; the colon is required
			if the move is part of a variation, precede the number with v, thus v27: 
			The actual numbers are in fact ignored (currently) by Go Recorder when importing the game! However the first numbered move determines where Go Recorder starts its numbering from, that is, Go Recorder will treat this as move number 1, preceding moves are regarded as setup or handicap stones. See above for controlling which moves are actually displayed on the diagram with a number.

<optional notation> this is a single character enclosed in square brackets, thus [A] ; the character will be displayed on the stone in the diagram

<optional comment> this is text to appear in the move information field as a game comment attached to the move; the first character of a comment must be a "hard" space (Option-space on Mac or Newton, ascii $CA); this initial character is stripped in the Newton game record.

<optional captures> a list of stones or notations to be captured by this move; precede the list with   (thus  C1 D2n ;  is Option-t on Mac and Newton, $A0 ); follow a position of a notation to be "captured" (removed) by  n to avoid capturing a stone at the same position. 

NOTE: It is not necessary to list all captures in the game record --- many formats, such as sgf, do not record this information. When importing such a game, after loading into the Newton's current game, turn off and then on the "Autocapture" option from the Options button menu: a dialog appears offering to run through the game and make all automatic captures. Of course it cannot remove notations or make non-automatic captures, such as removal of dead stones at the end of a game.

A notation entry looks like this
T16 [X] <optional comment> <optional captures>
The single character in the square brackets will be placed as an annotation on the point designated. When exporting a game record, Go Recorder starts a notation entry with some spaces to indent it. 

A game comment entry looks like this
<comment> <optional captures>
The comment must be preceded by a hard space. When exporting a record, Go Recorder will also start the line with three ordinary spaces to indent it, though this is not necessary.

A documentation comment is not part of the game itself, but is any text inserted into the record as a help to the reader or writer. Its format is
/<text>
that is, any line starting with  /  is ignored.

A Variation entry has two forms. The standard form is
 Variation <optional name>: <optional start clause> <optional comment>

<optional name> is a 1-character name for the variation

<optional start clause> if included should be of the form  
instead of 2: R19
This indicates that the variation replaces moves from R19 onwards; the move number (here 2:) is optional. Be careful that the starting point actually is legal, Go Recorder will not check for consistency.

The second form is a user-customised form. The word Variation can be replaced by any phrase, and the "instead of" clause (if needed) inserted after that phrase. Thus
 A different approach: instead of R19 Black could try

Variations must end with a line of the form
 Variation <optional name> ends.
